Release notes
TIP: Looking for release notes for all Axiom products, including current and previous versions? Click here.
NOTE: Download a PDF version of the release notes here.
New features
See What's new.
IMPORTANT: See the Technical Considerations section below for important information regarding the CostResultsUsage table and account number length in regards to invalid reclass and overhead allocation rules.
What to know before upgrading
IMPORTANT: You must apply the Axiom 2020.3 upgrade before applying any 2020.3 Axiom product upgrades. Axiom Software upgrades are backwards compatible so you can upgrade different products at different times, but you must upgrade to the Axiom 2020.3 before the first product upgrade. Refer to the Axiom 2020.3 Release Notes and Axiom Healthcare Suite 2020.3 Release Notes for considerations before upgrading. Apply this update ONLY if you have already applied the release and completed all the manual setup steps from the corresponding release notes.
When upgrading to the 2020.3.1 version of Axiom Enterprise Decision Support, keep in mind the following:
- This product upgrade contains updated templates, calculation methods, driver files, and remediated defects.
- KHA delivered reports may be removed or replaced. Any report that you saved under a different name or created new will remain untouched. Replaced reports are available in Document History, if needed.
- Any KHA delivered report that was moved to a new location by the client will automatically move back to its original location.
- KHA product templates and calculation method libraries will be replaced.
-
Process definitions will not be replaced. Process Manager will not currently work with the new system tables and web-based pages and utilities. Consequently, please plan on reviewing and potentially revising any Cost Accounting Process Definitions depending on the scope and what tasks have been created and are in use.
-
Security roles and sub-systems will be reset to their configured settings for the Axiom defined roles. All security exceptions you may have made at the individual user level will remain intact.
-
Specific items configured as part of your company or organization's implementation such as imports, exports, driver files, and process management files, will remain as is. Any required modifications to these areas are covered in the release notes, if required. For example, Process Manager defined processes for Cost Accounting will need to be modified by Client Success and has limitations with accessing web-based tasks.
Preparing for and scheduling upgrades
Summary of the upgrade process:
- Review product release notes – Review this document to familiarize yourself with the new features and functionality.
- Schedule an installation date – Submit a request to your organization's Axiom Master System User (MSU) to contact support by creating a support ticket to schedule an installation date and time with at least three days of advance notice. The request should include the following information:
- Desired Axiom platform version.
- Desired Axiom for Healthcare product and version.
- Indicate whether to first refresh the Axiom test sandbox with a copy of the production instance of Axiom and apply update(s) to it. If so, provide the soonest that Syntellis can do this.
- Propose an approximate two-hour downtime window when Syntellis can apply update(s) to the production instance of Axiom during regular business hours, Monday through Friday 7 AM to 7 PM Central (except holidays recognized by Syntellis).
- Complete manual configuration updates – After installing the upgrade, review any manual setup steps needed to enable features for this version.
Getting help and training
Syntellis provides world-class resources at your fingertips directly within the Axiom system. Axiom Help provides topics, knowledge base articles, documents, webinar/training announcements, and videos to guide you through managing your system. To access these resources, do any of the following:
-
Windows and Excel Clients – From the Main or Admin ribbon tab, click Online Help, and then select the product. Axiom Help opens in a new browser window.
NOTE: The online help will only open for products you are licensed to use.
-
Form/Web pages – Form/web-enabled features and products include contextual help directly within the user interface. This information provides a quick summary and/or instructions specifically related to the screen you are using. You can access this information by clicking the question mark in the upper right corner of the screen. To access the full Axiom Help system, click Open Help at the top of the contextual help dialog.
Syntellis Central
Syntellis Central provides centralized self-service content and resources for the Axiom Executive Decision Support platform and suite of products. Using Syntellis Central, you can:
- Search help across all Axiom products
- Access tips, tricks, and best practices in our knowledge base
- Find training & certification content including on-demand, video, webinars, labs, and instructor-led courses
- Submit a support issue, find suggested content, and manage any outstanding issues directly with us
- Review open Software Service project status and details
2020.3.1 - Known issues resolved
The following tables list the resolutions for issues addressed in 2020.3.1, released on October 12th, 2020:
| Issue | Description |
|---|---|
| Web UI: Delete button requires save after row has been deleted in dimension tables [TFS 32042] |
Issue: Currently, when a user clicks the Delete button when deleting a dimension row, the system displays a confirmation dialog to delete the row. When the user clicks OK', the user then also needs to click the Save button to confirm the deletion. This save action is not explained in the interface. Resolution: Corrected by no longer requiring the user to click the Save button when deleting a row. |
| PFB-07748 - Unit Cost Recon Reports Refresh Issue [TFS 38039] |
Issue: Some of the Unit Cost Reconciliation reports need to be refreshed twice to bring in the correct data. This was discovered in the "ReconUC_02_1_Cost Results to Costing GL by Dept" report but likely impacts other costing reports that are set up the same way. This only happens in the Excel Client. Resolution: Corrected by setting refresh in the Control Sheet between AQs. |
| PFB-08580 - Sum Cost Detail Category to Encounter Detail Category [TFS 44098] |
Issue: The Cost Assignment import utility, Sum Cost Detail Category to Encounter Detail Category in 2019.4 does not fully update the EDCC table from CDCC for encounters discharged based on the transaction start and end ServiceYRMO when run for a current or prior period (CostSet). Resolution: Corrected by removing additional constraints in the query that summarizes the Cost Detail Category Calculation (CDCC) table to the Encounter Detail Category Calculation (EDCC) table. |
| DSS Axiom Intelligence: Variable columns across 10 tables have "Included in AI Model" set to false, leading to lack of their usability in Axiom Intelligence reports [TFS 48304] |
Issue: The following tables with Group 1-5 variable columns should be included in the Axiom Intelligence model:
Resolution: Corrected by including the list of tables above into the model. |
2020.3.2 - Known issues resolved
No client facing issues were addressed in this release.2020.3.3 - Known issues resolved
| Issue | Description |
|---|---|
| Sum CDCC to EDCC job fails in large volume systems [TFS 61745] | Issue: When importing data using the Sum Cost Detail Category to Encounter Detail Category.axi ETL, the system displays an error message that the import failed. Resolution: Corrected by updating the ETL to load into the CDCC using smaller batches of data. |
2020.3.4 - Known issues resolved
The following table list the resolutions for issues addressed in 2020.3.4, released on January 11th, 2021:
| Issue | Description |
|---|---|
| PFB-09343 - Encounter Viewer error occurs when using zip codes with alpha numeric values [TFS 69384] | Issue: When using the Encounter Viewer, the system displays a conversion and incorrect syntax error when loading a patient. Resolution: Corrected the query that populates the Encounter Viewer page to allow zip codes with alpha numeric values. |
| PFB-09427 - Reclass defect [TFS 75191] | Issue: Axiom does not save more than one account number when defining the source. When adding two account numbers and then clicking the worksheet tab, the system presents the data, but when saving the reclass, the closing parenthesis is removed and an error message displays. Resolution: Corrected the syntax of the save mechanism because the saving mechanism for the reclass rule was erroneously removing the ending ")". |
2020.3.5 - Known issues resolved
The following table list the resolutions for issues addressed in 2020.3.5, released on February 15th, 2021:
| Issue | Description |
|---|---|
| 2020.3 CostDetailBase and CostDetailTotalCost allows duplicate transaction records [TFS 78820] | Issue: Running an import that saves to the CostDetailBase and updates an existing servicedate may cause a duplicate transaction to be created. Resolution: Corrected by adding a new transformation to the beginning of the CostDetailStaging to CostDetail import that updates the serviceyrmo for any transactionid where the imported serviceyrmo is different than the one stored in the database. IMPORTANT: See the Add new transformation step to customized version of Import CostDetail from Staging.axi for instructions on configuration steps you may need to complete related to this resolved defect. |
2020.3.6 - Known issues resolved
The following table list the resolutions for issues addressed in 2020.3.6, released on April 12th, 2021:
| Issue | Description |
|---|---|
| Service line groups are not available for reporting in 20.3 | Issue: Users cannot report on service line groups in the Windows/Excel client in the 20.3 implementation of service lines. This only affects clients who upgrade to Axiom 20.3 AND migrate their service lines and groups to the 20.3 service line model. Resolution: Corrected by creating an install script that moves Groups to the new fields on the ServiceLine Assignment table. |
2020.3.7 - Known issues resolved
No end-user facing issues addressed in this release.
2020.3.8 - Known issues resolved
No end-user facing issues addressed in this release.
Add new transformation step to customized version of Import CostDetail from Staging.axi
A new transformation step has been added to \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi that prevents duplicate record creation in the CostDetailBase table. Many clients use a customized version of this import, so you may need to add this new transformation step to your version.
The best way to do this is to identify the import that your organization uses to import cost detail records and, if the version you are using does not point to \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi, then you will need to copy transfromation step 1 from \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi to your version.
CostResultsUsage table
In Axiom Cost Accounting 2019.4 Patch 1, it was discovered that the CostResultsUsage table was no longer referred to by the original reports it was meant to support. To improve cost processing performance, we deprecated the table, and as a result, the system no longer writes data to the table.
IMPORTANT: If your organization uses exports or reports that use data points from this table, you will need modify the exports/reports to point them to point them to tables post 2019.4 upgrade.
Account number lengths and invalid reclass/overhead allocation rules
Post 2019.1, the system identifies reclass and overhead allocation rules as invalid if the associated account numbers are less than 13 digits. Review the following process diagram to determine the appropriate steps to resolve this issue.
Click image to view full size
Custom Encounter Patient imports and patient zip codes
If your organization uses a custom version of the Encounter Patient import from previous versions of Axiom, you may encounter an error when importing zip codes if they do not currently exist in the PatientZipcode table.
You can resolve this issue one of the following ways:
Add a transform step to your custom Encounter Patient import that adds all zip codes from the import to the PatientZipcode table.
Copy the standard 2020.3 Encounter Patient import, and customize it as needed. This import includes the step to add zip codes to the PatientZipcode table.
Complete these steps to add a new transform step:
Open your customized Encounter Patient import.
In the Transforms tab, click any of the Add new dimension elements transform steps, and then click + in the upper right corner of the dialog to add the new step. In the following screen shot, the new transform will be added after step 15.
In the new row that displays, click the ellipsis (...).
In the Edit Transform dialog, select Built-in Function.
From the Function drop-down, select Add new dimension elements.
In the Table field, type PatientZipcode.
Click OK.
